User interface method and apparatus for mobile terminal having touchscreen

ABSTRACT

A user interface method and apparatus for a mobile terminal having a touchscreen are provided. The apparatus and method improve interactivity using a toolbar menu mode screen which allows a user to execute functions and commands with drag and drop behaviors on the touchscreen to graphical objects such as toolbar, icons, and other active objects. An interface apparatus includes a touchscreen unit that displays a screen including a second region for presenting a toolbar having at least one User Interface (UI) element representing a specific function and a first region for activating, when the UI element is dragged from the toolbar and dropped in the first region on the touchscreen, the function represented by the UI element. The interface apparatus also includes a control unit which detects a drag and drop action of the UI element and activates, when the drag and drop action is detected, the function associated with the UI element in the form of an active function object. The interface apparatus of the present invention registers the frequently used functions with the toolbar in the form of icons such that, when an icon is dragged from the toolbar to the main window, the function represented by the icon is activated.

CLAIMS OF PRIORITY

This application is a continuation application of a prior applicationSer. No. 12/346,156, filed on Dec. 30, 2008, which claimed the benefitunder 35 U.S.C. § 119(a) of a Korean patent application filed in theKorean Intellectual Property Office on Mar. 7, 2008 and assigned SerialNo. 10-2008-0021559, the entire disclosure of each of which is herebyincorporated by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention:

The present invention relates to the control of a mobile terminal Moreparticularly, the present invention relates to a user interface methodand apparatus for a mobile terminal having a touchscreen.

2. Description of the Related Art:

With the recent tendency toward functional convergence, mobile terminalsare becoming versatile multimedia devices including various integratedsupplementary functions such as an electronic dictionary, games,scheduler functions and the like. As the capability and functions of themobile terminal is diversified, a convenient user interface is becomingan influential factor for improving the utilization of the mobileterminal. For this reason, various user interface mechanisms have beendeveloped and proposed for facilitating manipulation of the mobileterminal. One promising user interface mechanism is a touchscreen.

A touchscreen is a display device that can detect the presence andlocation of a touch within the display area, whereby a user can executea command or place a cursor by contacting a specific position on thedisplay area with a finger or a device such as a stylus. There are threetypes of touchscreen mechanisms that are distinguished by the manner inwhich they recognize a touch: Resistive, Capacitive, and SurfaceAcoustic Wave (SAW). A resistive touchscreen mechanism senses a touch onthe screen by detecting a change in resistance at a position between twospaced layers of the touchscreen panel, caused by a touch event. Acapacitive touchscreen mechanism senses a touch on the screen bydetecting a position at which the electric charge on a capacitive layerdecreases. Finally, the SAW touchscreen mechanism senses a touch on thescreen by detecting a position at which ultrasonic waves, such asinfrared waves, passing over the panel are absorbed.

However, most of the conventional touchscreen-based user interfacetechnologies have been developed for use with relatively largeinteractive display panels and it is difficult to adopt the conventionaltouchscreen user interfaces to a mobile terminal because of its limiteddisplay size. Accordingly, there is a need to develop atouchscreen-based user interface method and apparatus that is capable offacilitating interaction with a mobile terminal having a smaller displaysize.

SUMMARY OF THE INVENTION

An aspect of the present invention is to address at least theabove-mentioned problems and/or disadvantages and to provide at leastthe advantages described below. Accordingly, an aspect of the presentinvention is to provide a user interface method and apparatus for amobile terminal having a touchscreen that is capable of improvinginteractivity with the mobile terminal using a toolbar menu mode screenwhich allows a user to execute functions and commands with drag and dropbehaviors on the touchscreen to graphical objects such as toolbar,icons, and other active objects.

In accordance with an aspect of the present invention, an interfaceapparatus for a mobile terminal is provided. The apparatus includes atouchscreen unit for displaying a screen including a second region forpresenting a toolbar having at least one User Interface (UI) elementrepresenting a specific function and a first region for activating, whenthe UI element is dragged from the toolbar and dropped in the firstregion on the touchscreen, the function represented by the UI element,and a control unit for detecting a drag and drop action of the UIelement and for activating, when the drag and drop action is detected,the function associated with the UI element in the form of an activefunction object.

In accordance with another aspect of the present invention, an interfacemethod for a mobile terminal having a touchscreen is provided. Themethod includes displaying a screen including a second region forpresenting a toolbar having at least one User Interface (UI) elementrepresenting a function and a first region and activating, when the UIelement is dragged from the toolbar and dropped in the first region onthe touchscreen, the function represented by the UI element in the formof an active function object within the first region.

Other aspects, advantages, and salient features of the invention willbecome apparent to those skilled in the art from the following detaileddescription, which, taken in conjunction with the annexed drawings,discloses exemplary embodiments of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features and advantages of certainexemplary embodiments of the present invention will be more apparentfrom the following description taken in conjunction with theaccompanying drawings, in which:

FIG. 1a is a diagram illustrating a toolbar menu mode screen of a mobileterminal according to an exemplary embodiment of the present invention;

FIG. 1b is a screenshot illustrating a toolbar menu mode screen of FIG.1 a;

FIG. 2a is a diagram illustrating a normal menu mode screen of a mobileterminal according to an exemplary embodiment of the present invention;

FIG. 2b is a screenshot illustrating a normal menu mode screen of FIG. 2a;

FIG. 3 is a diagram illustrating a configuration of a mobile terminalhaving a touchscreen according to an exemplary embodiment of the presentinvention;

FIG. 4 is a diagram illustrating a configuration of an exemplary toolbardriver of FIG. 3;

FIG. 5 is a diagram illustrating a toolbar menu registration settingscreen displayed on the touchscreen unit of a mobile terminal accordingto an exemplary embodiment of the present invention;

FIGS. 6a and 6b are diagrams illustrating a process of initializing atoolbar menu mode screen and showing a toolbar in a toolbar menu modescreen according to an exemplary embodiment of the present invention;

FIGS. 6c and 6d are diagrams illustrating processes of realigning atoolbar menu mode screen according to exemplary embodiments of thepresent invention;

FIGS. 6e and 6f are diagrams illustrating a process of activating afunction matched with an icon placed on a toolbar in a toolbar menu modescreen according to an exemplary embodiment of the present invention;

FIGS. 6g and 6h are diagrams illustrating a process of deactivating anactive function in a toolbar menu mode screen according to an exemplaryembodiment of the present invention;

FIG. 7 is a diagram illustrating a process of informing of a functionmatched with an icon selected on a toolbar in a toolbar menu mode screenaccording to an exemplary embodiment of the present invention;

FIGS. 8a and 8b are diagrams illustrating a process of activatingmultiple functions in a toolbar menu mode screen according to anexemplary embodiment of the present invention;

FIG. 9 is a diagram illustrating a process of realigning active functionobjects in a toolbar menu mode screen according to an exemplaryembodiment of the present invention;

FIGS. 10a and 10b are diagrams illustrating a process of zooming in onan active function object in a toolbar menu mode screen according to anexemplary embodiment of the present invention;

FIG. 10c is a screenshot illustrating a toolbar menu mode screen shownin the zooming-in process of FIGS. 10a and 10 b;

FIG. 11 is a flowchart illustrating a procedure of registering functionswith a toolbar in a user interface method according to an exemplaryembodiment of the present invention;

FIG. 12 is a flowchart illustrating a procedure of activating a functionregistered with a toolbar in a user interface method according to anexemplary embodiment of the present invention;

FIGS. 13a and 13b are diagrams illustrating operations of a function ina toolbar menu mode of a user interface method according to an exemplaryembodiment of the present invention;

FIG. 14 is a flowchart illustrating an exemplary function executionprocess of FIGS. 13a and 13 b;

FIGS. 15a to 15c are diagrams illustrating operations of a function in atoolbar menu mode of a user interface method according to an exemplaryembodiment of the present invention;

FIG. 16 is a flowchart illustrating an exemplary function executionprocess;

FIGS. 17a to 17c are diagrams illustrating operations of a function in atoolbar menu mode of a user interface method according to an exemplaryembodiment of the present invention;

FIG. 18 is a flowchart illustrating an exemplary function executionprocess;

FIGS. 19a and 19b are diagrams illustrating operations of a function ina toolbar menu mode of a user interface method according to an exemplaryembodiment of the present invention;

FIG. 19c is a screenshot illustrating a toolbar menu mode screendisplayed in association of the function execution process of FIGS. 19aand 19b ; and

FIG. 20 is a flowchart illustrating an exemplary function executionprocess.

Throughout the drawings, it should be noted that like reference numbersare used to depict the same or similar elements, features andstructures.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

The following description with reference to the accompanying drawings isprovided to assist in a comprehensive understanding of exemplaryembodiments of the invention as defined by the claims and theirequivalents. It includes various specific details to assist in thatunderstanding but these are to be regarded as merely exemplary.Accordingly, those of ordinary skill in the art will recognize thatvarious changes and modifications of the embodiments described hereincan be made without departing from the scope and spirit of theinvention. Also, descriptions of well-known functions and constructionsare omitted for clarity and conciseness.

The terms and words used in the following description and claims are notlimited to the bibliographical meanings, but, are merely used by theinventor to enable a clear and consistent understanding of theinvention. Accordingly, it should be apparent to those skilled in theart that the following description of exemplary embodiments of thepresent invention are provided for illustration purpose only and not forthe purpose of limiting the invention as defined by the appended claimsand their equivalents.

By the term “substantially” it is meant that the recited characteristic,parameter, or value need not be achieved exactly, but that deviations orvariations, including for example, tolerances, measurement error,measurement accuracy limitations and other factors known to skill in theart, may occur in amounts that do not preclude the effect thecharacteristic was intended to provide.

In the following description, the mobile terminal can be any of aPersonal Digital Assistant (PDA), a Smartphone and a cellular networkterminal including a Code Division Multiple Access (CDMA) terminal, aWideband CDMA (WCDMA) terminal, a General System for Mobilecommunications (GSM) terminal, a General Packet Radio System (GPRS)terminal and their equivalent devices. Furthermore, the mobile terminalis provided with a partial touchscreen or a full touchscreen.

In the following description, the term “touch” denotes a contact eventon the touchscreen using a finger or an object such as stylus. The term“drag” denotes a behavior of sliding the finger or object on thetouchscreen in a direction.

The term “toolbar menu mode” denotes an operation mode in which atoolbar having a plurality of icons is activated on the touchscreen suchthat, when one of the icons are dragged from the toolbar and dropped ina main display window, an application represented by the icon isactivated. As will be explained below, the toolbar may be located on aside of the touchscreen.

The term “Top-3 icon” denotes a shortcut icon presented with informationabout a number of counterparty persons selected from a phonebook so asto make a voice call, a message call, or video call, immediately.Although the number “3” is used in the term, it should not be considereda limitation on the number of counterparty persons included as there mayany number including three.

The toolbar may include at least one User Interface (UI) elementassociated with a specific function. The UI element may be presented inthe form of an icon.

In the following description, the term “active icon” denotes an iconindicating an active state of an application which is activated bydragging a corresponding UI element (e.g. icon) from the toolbar anddropping the UI element in the main display window.

In the following description, it is to be understood that the singularforms “a,” “an,” and “the” include plural referents unless the contextclearly dictates otherwise. Thus, for example, reference to “a componentsurface” includes reference to one or more of such surfaces.

FIG. 1a is a diagram illustrating a toolbar menu mode screen of a mobileterminal according to an exemplary embodiment of the present invention.The toolbar menu screen is provided with a toolbar 120, a plurality oficons 110 arranged on the toolbar, the icons representing correspondingapplications, a first region 130 as a main display area of the mobileterminal, a second region 140 for placing the toolbar 120, a marker 150for hiding and showing the toolbar 120, and a plurality menu buttons 160a, 160 b, 160 c, and 160 d for executing corresponding functions of themobile terminal. In the example of FIG. 1a , the toolbar 120 ispositioned on a left side of a display area. However, this location ismerely for example and it is understood that the toolbar 120 may belocated elsewhere.

The icons 110 are designed with pictures or symbols symbolizingfunctions of the corresponding applications in order for a user torecognize the applications intuitively.

The toolbar 120 provides the user with an application activationinterface such that the user may perceive and activate the applicationsas desired. The icons 110 can be arranged in a horizontal or verticaldirection. In FIG. 1a , the icons 110 are arranged on the toolbar 120 inthe vertical direction.

The first region 130 is a main display window on which the applicationsare executed and execution results are displayed in a visual informationform. The first region 130 may be configured to display a specific imagewith a specific color theme. In this example, if any of the icons 110arranged on the toolbar 120 is moved to the first region 130, then theapplication represented by the icon is activated.

The second region 140 may be defined on a side of the touchscreen forplacing the toolbar 120 and resized in a direction according to whetherthe toolbar 120 is hidden or shown. The behavior of the second region140 is described in more detail with reference to FIGS. 6a to 6h later.

The menu buttons 160 a to 160 d may be provided on a menu bar of thetouchscreen for quick execution of desired menus or applications. In theillustrated example, the menu buttons 160 a to 160 d are positioned atthe bottom of the touchscreen. However, the menu buttons may bepositioned elsewhere as desired by the user or as required by theexecution of other display operations. Also, although the menu bar isdepicted with a dial button 160 a for making a call, a phonebook button160 b for loading a phonebook, a message button 160 c for checkingincoming and outgoing message boxes, and a main menu button 160 d forloading the main menu of the mobile terminal in this example, the menubuttons can be replaced by other menu buttons or removed from the menubar.

FIG. 1b is a screenshot illustrating a toolbar menu mode screen of FIG.1a . Although not individually labeled, the illustrated toolbar menumode screen shows icons 110, toolbar 120, marker 150, and menu buttons160 a to 160 d that may be displayed on the touchscreen.

As illustrated in FIG. 1b , the toolbar 120, on which the icons 110 arearranged in vertical direction, is placed on the second region 140. Theicons 110 include a date and day icon, a D-day icon, an album icon, awireless Internet access icon, a Top-3 function icon and others. In thefirst region 130, a clock and a subway map are activated.

When an icon is dragged from the toolbar 120 and dropped in the firstregion 130, an application represented by the icon is activated in thefirst region 130, whereby the user can execute the applicationsintuitively.

FIG. 2a is a diagram illustrating a normal menu mode screen of a mobileterminal according to an exemplary embodiment of the present invention.In the normal menu mode, the mobile terminal displays a normal menu modescreen having a plurality of menu icons 210, 220, 230, 240, 250, and260, and a menu bar with a plurality of menu buttons 270 a, 270 b, 270c, and 270 d.

The menu icons 210 to 260 are icons representing applications orfunctions that are most frequently used by the user. The menu icons maybe replaced with other icons, additional icons may be included, or someof the menu icons may be removed from the normal menu mode screen. Inthis exemplary embodiment, the normal menu mode screen shows a cameraicon 210, an album icon 220, a game icon 230, a TV icon 240, a musicicon 250, and a setting icon 260. Of course, the functions representedby these icons are merely for example.

The menu buttons 270 a to 270 d are provided on the menu bar of thenormal menu mode screen for quick execution of frequently used menus. Inthe illustrated example, the menu bar is positioned at the bottom of thenormal menu mode screen. However, the menu bar may be positionedelsewhere on the normal menu mode screen. Although the menu bar isdepicted with a dial button 270 a for making a call, a phonebook button270 b for loading the phonebook, a message button 270 c for checkingincoming and outgoing message boxes, and a mode switching button 270 dfor switching to the toolbar menu mode, the menu buttons can be replacedby other menu buttons or removed from the menu bar.

When the mode switching button 270 d is selected, the menu mode screenis switched from the normal menu mode screen to the toolbar menu modescreen, an example of which was illustrated in FIG. 1a . In a case thatthe toolbar menu mode screen is selected, the display is switched to thetoolbar menu mode screen which is presented with the settings of theprevious toolbar menu mode session.

FIG. 2b is a screenshot illustrating a normal menu mode screen of FIG.2a . The illustrated normal menu mode screen shows the icons and menubar that may be presented on the touchscreen of the mobile terminal.

As illustrated in FIG. 2b , a main window of the touchscreen presents awireless Internet access icon, a camera icon, an album icon, a gameicon, a TV icon, a music icon, a memo icon, a function icon, a schedulericon, an alarm and time icon, a dictionary icon, and a settings iconarranged in 3 by 4 alignment. However, the number, kinds and alignmentof the icons can be changed by the user.

FIG. 3 is a diagram illustrating a configuration of a mobile terminalhaving a touchscreen according to an exemplary embodiment of the presentinvention. As illustrated FIG. 3, the mobile terminal includes a RadioFrequency (RF) unit 310, a Bluetooth unit 320, an audio processing unit330, a sensing unit 340, a storage unit 350, a touchscreen unit 360, anda control unit 370. The control unit 370 includes a toolbar manager 370a and a toolbar driver 370 b.

The RF unit 310 includes an RF transceiver and a duplexer for processingan RF signal transmission and reception of the mobile terminal.

The Bluetooth unit 320 includes a Bluetooth transmitter and a Bluetoothreceiver for communication with a Bluetooth link of a Bluetooth-enableddevice.

The audio processing unit 330 is provided with a microphone (MIC) forconverting sound into an audio signal and a speaker (SPK) for convertingan audio signal into an audible sound.

The sensing unit 340 senses a rotation of the mobile terminal. In anexemplary implementation, the sensing unit 340 may be implemented with aterrestrial magnetic sensor. The terrestrial magnetic sensor measuresthe strength and direction of the terrestrial magnetism and outputs ameasurement value. In an exemplary embodiment, the sensing unit 340senses the rotation of the mobile terminal and outputs the measurementto the control unit 370 such that the control unit 370 controls an iconplaced on the toolbar to rotate in accordance with the rotation of themobile terminal. That is, the icon is controlled to rotate so as to beeasily viewable by the user.

The storage unit 350 may include a long term memory, such as a Read OnlyMemory (ROM) or a flash memory, and a short term memory such as a RandomAccess Memory (RAM). The long term memory stores application programsrequired for the operations of the mobile terminal as well as dataentered by a user, such as a phone number. The short term memory storestemporary data that is generated during operation of the mobileterminal.

The touchscreen unit 360 includes a display panel 360 a and a touchpanel or a touch film 360 b. The touchscreen unit 360 may displayvarious visual data produced in the mobile terminal, operation status ofthe mobile terminal data input by the user and the like. The touchscreenunit 360 also senses a touch on the touch film 360 b and outputs acoordinate of the point of contact to the control unit 370. Thetouchscreen unit 360 may be implemented with any of the resistive,capacitive, and Surface Acoustic Wave (SAW) type mechanisms.

In an exemplary embodiment, the display panel 360 a of the touchscreenunit 360 is implemented to display the toolbar menu mode screen and thenormal menu mode screen as switchable user interfaces for executingfunctions of the mobile terminal thereon.

The control unit 370 controls general operations of the mobile terminal.For example, the control unit 370 controls the Bluetooth unit 320 toestablish a Bluetooth link with a Bluetooth device located in itsBluetooth radio range. Also, the control unit 370 analyzes a measurementsignal sent by the sensing unit 340 (i.e. the terrestrial magneticsensor) and controls such that an icon placed on the toolbar rotates inaccordance with the rotation of the mobile phone.

In an exemplary embodiment, the control unit 370 includes a toolbarmanager 370 a and a toolbar driver 370 b.

When the mobile terminal enters a toolbar menu registration settingmode, the toolbar manager 370 a generates a function list listingfunctions that can be registered to the toolbar 120 and displays thefunction list on the display panel 360 a of the touchscreen unit 360. Ifa function is selected from the function list, then the toolbar manager370 a updates a setting information file by matching the function with acorresponding icon 110. Table 1 shows an exemplary setting informationfile.

TABLE 1 Icon Function Photo album icon Load Image viewer ABC charactericon Open dictionary Top-3 icon Make voice, message, and video call, andthe like Clock icon Display Present time — — — — — —

An icon 110 is designed with a picture, a symbol, or a characterassociated with the function represented by the icon such that the userrecognizes the function intuitively. For example, the camera function ismatched to an icon designed having a camera picture.

When the mobile terminal enters the toolbar menu mode, the toolbardriver 370 b retrieves the functions registered for the toolbar anddisplays the toolbar including the icons matched with their registeredfunctions. The toolbar driver 370 b also receives the settinginformation file (e.g. table 1) from the toolbar manager 370 a andstores the received setting information file. If it is detected that aspecific icon 110 is moved from the toolbar 120 to the first region 130,then the toolbar driver 370 b looks up the setting information file andactivates the function matched with the icon moved to the first region130.

FIG. 4 is a diagram illustrating a configuration of an exemplary toolbardriver of FIG. 3. The toolbar driver 370 b includes a toolbarinformation configuration module 410, a toolbar presentation module 420,and a function execution module 430.

Referring to FIG. 4, the toolbar information configuration unit 410receives and stores the setting information file generated in the formof a table matching the icons 110 with the functions that are supposedto be executed when corresponding icons are moved to the first region130 of the toolbar menu mode screen. When the mobile phone enters thetoolbar menu mode, the toolbar presentation module 420 retrieves thefunctions registered to the toolbar and presents the toolbar includingthe icons matched with the registered function on the display panel.When a specific icon is moved from the toolbar 120 to the first region130, the function execution module 430 looks up the setting informationfile and executes the function corresponding to the icon moved to thefirst region 130.

FIG. 5 is a diagram illustrating a toolbar menu registration settingscreen displayed on a touchscreen unit of a mobile terminal according toan exemplary embodiment of the present invention.

When the mobile terminal enters the toolbar menu registration settingmode, the toolbar manager 370 a retrieves the function list and presentsthe function list listing the function items. In an exemplaryimplementation, check boxes are also presented such that the user canselect the functions of which icons are to be presented on the toolbarby selectively marking the checkboxes. Of course, other methods ofselecting the desired functions may be implemented, for examplehighlighting the selected functions.

Exemplary operations of the touchscreen in the toolbar menu mode aredescribed hereinafter with reference to FIGS. 6a to 6h , 7, 8 a and 8 b,9, and 10 a to 10 c.

First Exemplary Embodiment

FIGS. 6a and 6b are diagrams illustrating a process of initializing atoolbar menu mode screen and showing a toolbar in a toolbar menu modescreen according to an exemplary embodiment of the present invention.

Referring to FIG. 6a , if the mobile terminal first enters the toolbarmenu mode, then the touchscreen unit 360 displays a toolbar menu modescreen substantially empty except for a marker 610 as shown in FIG. 6a .If a touch is detected on the marker 610, the touchscreen unit 360presents the toolbar 120 in the toolbar menu mode screen as shown inFIG. 6 b.

In this manner, the control unit 370 can be configured such that thetoolbar menu mode starts with the empty toolbar menu mode screen and thetoolbar appears by selecting the marker 610. In an exemplaryimplementation, the marker 610 can be designed as an iconic objectimplying a direction. For example, the marker 610 may have the shape ofan arrowhead in the form of an equilateral triangle. Prior to display ofthe toolbar 120, the marker 610 is displayed pointing to the right inthe empty toolbar menu mode screen. If the marker 610 is selected andthe toolbar 120 appears in the toolbar menu mode screen, the pointingdirection of the marker 610 may be changed to the left so as to face thenow displayed toolbar 120.

That is, the control unit 370 controls such that, when the toolbar isactivated to appear in the toolbar menu mode screen, the marker 610rotates 180° so as to point to the opposite direction. Also, when atouch on the marker 610 is detected while the toolbar appears, thecontrol unit 370 controls such that the marker 610 is changed to pointto the left and controls to cause the disappearance of the toolbar 120.

FIGS. 6c and 6d are diagrams illustrating processes of realigning atoolbar menu mode screen according to exemplary embodiments of thepresent invention.

When the orientation of the mobile terminal is altered, the sensing unit340 senses the alteration of the mobile terminal and outputs a sensedalteration value to the control unit 370 such that the control unitdetermines the orientation of the mobile terminal based on thealteration value. The control unit 370 can control such that, when theorientation of the mobile terminal is changed, the orientations of thetoolbar and icons placed on the toolbar are changed depending on thedirection of the changed orientation of the mobile terminal.

In this exemplary embodiment, when the orientation of the mobileterminal changed from a portrait orientation to a landscape orientation,the orientations of the icons placed on the toolbar and the menu buttonsplaced on the menu bar are changed without change of the positions andorientations of the toolbar and the menu bar, as shown in FIG. 6 c.

For example, when the control unit 370 detects that the orientation ofthe mobile terminal rotates at 90° in clockwise direction, it controlssuch that the icons placed on the toolbar rotate at 90° incounterclockwise direction. Also, when the control unit 370 detects thatthe mobile terminal rotates at 90° in counterclockwise direction, fromthe portrait orientation to the landscape orientation, it controls suchthat the icons placed on the toolbar rotate at 90° in clockwisedirection.

The control unit 370 also controls the rotation of the menu buttons 160a to 160 d placed on the menu bar and indicators (such as a batteryindicator, a radio strength indicator, and a present time indicator)placed on a status indication bar within the toolbar menu mode screen inthe same manner.

As shown in FIG. 6d , the toolbar menu mode screen may be configuredsuch that, when the orientation of the mobile terminal rotates from theportrait orientation to the landscape orientation in clockwisedirection, the toolbar, menu bar, and status indication bar revolverelative to the display panel in opposite direction.

For example, when the control unit 370 detects that the orientation ofthe mobile terminal rotates 90° in clockwise direction, it controls suchthat the toolbar, menu bar, and status indication bar revolve relativeto the display panel in counterclockwise direction. Also, when thecontrol unit 370 detects that the mobile terminal rotates at 90° incounterclockwise direction, from the portrait orientation to thelandscape orientation, it controls such that the toolbar, menu bar, andstatus indication bar revolve relative to the display panel in clockwisedirection.

FIGS. 6e and 6f are diagrams illustrating a process of activating afunction matched with an icon placed on a toolbar in a toolbar menu modescreen according to an exemplary embodiment of the present invention.

As shown in FIG. 6e , if the user drags a specific icon 630 a from thetoolbar 120 and drops the icon 630 a in the first region, the toolbardriver 370 b looks up a matching table stored as the setting informationfile and activates the function matched with the icon 630 a in thematching table. Here, the control unit 370 controls such that, when anicon 630 a is dragged out of the toolbar 120 and its correspondingfunction 630 b is executed on the first region, another function icon640 is placed at the position as shown in FIG. 6f . The function icon640 replacing the icon 630 a can be selected from candidate functionicons registered for the toolbar 120.

FIGS. 6g and 6h are diagrams illustrating a process of deactivating anactive function in a toolbar menu mode screen according to an exemplaryembodiment of the present invention.

As shown in FIG. 6g , the user can drag an active function object fromthe main window and drop the active function object on the toolbar 120.In this case, the toolbar driver 370 controls such that the icon matchedwith the active function object retrieved from the setting informationfile is placed on the toolbar 120.

For example, if the user drags an active function object 630 b from themain window and drops the active function object 630 b between the icons650 and 660 on the toolbar 120, then an icon 630 a matched with theactive function object 630 b is placed between the icons 650 and 660 asillustrated in FIG. 6 h.

FIG. 7 is a diagram illustrating a process of informing of a functionmatched with an icon selected on a toolbar in a toolbar menu mode screenaccording to an exemplary embodiment of the present invention.

In some cases, the user may not recognize the functions associated withthe respective icons 110 placed on the toolbar, upon first glance or dueto poor eyesight.

Accordingly, in order to provide the user with information about thefunctions matched with the icons 110, the control unit 370 controls suchthat, when a touch is detected on an icon, the information on thefunction represented by the icon is presented in the form of a balloontext 710. As illustrated in FIG. 7, if the user touches on the “ABC”icon, then the control unit 370 controls such that a balloon text 710 isdisplayed with the text “Dictionary” to inform the user that the iconrepresents the dictionary function.

The additional information about the function represented by theselected icon may be provided by another method, e.g. with an enlargedicon or a voice announcement.

Accordingly, even when the user has poor eyesight or does not recognizethe functions represented by the icons, it is possible to obtain theinformation on the functions associated with the icons by touching onthe icons, resulting in improvement of user convenience.

FIGS. 8a and 8b are diagrams illustrating a process of activatingmultiple functions in a toolbar menu mode screen according to anexemplary embodiment of the present invention.

Since the first region 130 of the toolbar menu mode screen is limited insize, the active function objects 810 and 820 that are activated bymoving their corresponding icons from the toolbar to the first region130 are allowed to be overlappingly displayed within the first region130.

In FIG. 8a , the first active function object 810 is partiallyoverlapped with the second active function object 820. In this case, thefirst and second active function objects 810 and 820 can be adjusted intransparency under the control of the control unit 370 such that, evenwhen the first and second active function objects are overlapped, theuser can acquire the information provided by both the first and secondactive function objects simultaneously.

FIG. 8b shows another exemplary situation in which two active functionobjects 810 and 820 are overlappingly displayed in the first region 130.In this case, the first and second active function objects 810 and 820are presented opaquely such that the second active function object 820is hidden by the first active function object 810 at the overlappedportion.

FIG. 9 is a diagram illustrating a process of realigning active functionobjects in a toolbar menu mode screen according to an exemplaryembodiment of the present invention. In FIG. 9, two active functionobjects 810 and 820 are overlappingly arranged on different depth planesin the toolbar menu mode screen.

If the second active function object 820 is selected by a touch eventwhile the first active function object 810 overlies the second activefunction object 820 as shown in FIGS. 8a and 8b , the control unit 370controls such that the second active function object 820 is placed on ahigher plane such that the second active function object 820 overliesthe first active function object 810.

In this case, the control unit can control such that some parts of thefirst active function object 810 (in FIG. 9, a hour hand and a minutehand of a clock) are placed on the higher plane to improve readabilityof information provided by the first active function object 810 (in FIG.9, present time of the clock) even though the first active functionobject 810 is placed on a lower plane.

FIGS. 10a and 10b are diagrams illustrating a process of zooming in onan active function object in a toolbar menu mode screen according to anexemplary embodiment of the present invention, and FIG. 10c is ascreenshot illustrating a toolbar menu mode screen shown in thezooming-in process of FIGS. 10a and 10 b.

As shown in FIG. 10a , a clock 1020 as the first active function objectand a subway map 1030 as the second active function object are presentedin the first region 130 of the toolbar menu mode screen. Since the clockis provided in the form of a simple image and the information (presenttime) provided by the clock is also relatively simple, the user can readthe information (present time) with no difficulty. However, the subwaymap 1030 includes much information (including stations, junctionstations, types of subway lines, and stop-by stations), making itdifficult for the user to read the information on the subway map 1030 asit is displayed.

In this exemplary embodiment, when a zoomable active function object(e.g. subway map 1030) is selected by touch, a zoom function object 1010having zoom-in and zoom-out buttons 1012 and 1014 is activated.

If a touch is detected on the zoom-in button 1012, then the control unit370 controls to zoom in on the zoomable active function object. In theexample as shown in FIG. 10b , the user can zoom in on the subway map1030 by touching the zoom-in button 1012 such that the user can readinformation that is difficult to see before the subway map 1030 iszoomed in. In this manner, the user can acquire the information such asa station name, junction stations, subway lines, and stop-by stationsfrom the subway map 1030. Also, while the subway map 1030 is zoomed, theuser can more easily navigate on the subway map 1030.

The control unit 370 also can control such that, when a touch isdetected on the zoom-in button 1012, the first region 130 is zoomed inat a certain percentage. In this case, when a touch is detected on thezoom-out button 1014, the control unit 370 controls such that the firstregion 130 is zoomed out at the certain percentage.

As shown in FIG. 10c , the toolbar menu mode screen is provided with thezoom-in and zoom-out buttons 1012 and 1014, and the first region 130 iszoomed in by touch on the zoom-in button 1012.

Using the zoom-in and zoom-out buttons 1012 and 1014, the user can zoomin and out the first region 130 at a certain percentage.

FIG. 11 is a flowchart illustrating a procedure of registering functionswith a toolbar in a user interface method according to an exemplaryembodiment of the present invention.

Referring to FIG. 11, the control unit 370 of the mobile terminaldetermines whether a toolbar menu registration mode command is detectedin step S1110.

If a toolbar menu registration mode command is detected, the controlunit 370 retrieves a toolbar menu function list listing the functionsthat can be registered with the toolbar in step S1130 and displays thefunctions in step S1140. In an exemplary embodiment, the functions maybe displayed with check boxes as illustrated in FIG. 5 or otherselection options. While displaying the functions, the control unit 370determines if one of the functions is selected for registration in stepS1150. For example, the user can select the functions to be registeredwith the toolbar by marking on the check boxes provided with thefunctions. If a function is selected, the control unit 370 creates (orupdates) setting information, i.e. a matching table (see table 1) inwhich a function icon is matched with the function selected by the userin step S1160, and stores the matching table in the storage unit 350 instep S1170.

FIG. 12 is a flowchart illustrating a procedure of activating a functionregistered with a toolbar in a user interface method according to anexemplary embodiment of the present invention.

Referring to FIG. 12, the control unit 370 determines whether the mobileterminal is operating in a toolbar menu mode in step S1210. If themobile terminal is not operating in the toolbar menu mode, then thecontrol unit 370 determines that the mobile terminal is operating in anormal menu mode and controls to provide a normal menu mode service instep S1220.

Otherwise, if it is determined that the mobile terminal is operating inthe toolbar menu mode in step S1210, the control unit waits for thedetection of a touch on a marker provided on a toolbar menu mode screenin step S1230. If a touch on the marker is detected, the control unitchecks the functions registered with the toolbar and controls such thatthe toolbar on which the icons matched with the functions are placed ispresented in the toolbar menu mode screen in step S1240. In a case thatthe toolbar menu mode screen is provided without the marker, the controlunit checks the functions registered with the toolbar and presents thetoolbar in the toolbar menu mode screen together with the icons matchedwith the functions, in response to a detection of a touch at anyposition on the touchscreen. In an exemplary implementation, theposition can be a predetermined position or an empty area having noicon.

Next, the control unit determines whether an icon placed on the toolbaris dragged and dropped in a main window 130 of the toolbar menu modescreen in step S1250. If it is detected that an icon is dragged from thetoolbar and dropped in the main window 130, the control unit checks thefunction matched with the icon with reference to the matching table instep S1260 and activates the function matched with the icon in the mainwindow in step S1270.

The user interface methods according to second to fifth exemplaryembodiments of the present invention are described with reference toFIGS. 13a and 13b , 14, 15 a to 15 c, 16, 17 a to 17 c, 18, 19 a to 19c, and 20.

Second Exemplary Embodiment

FIGS. 13a and 13b are diagrams illustrating operations of a function ina toolbar menu mode of a user interface method according to an exemplaryembodiment of the present invention. In this exemplary embodiment, thefunction execution process is described with reference to activation ofa clock function by dragging a clock icon representing the clockfunction from a toolbar and dropping the clock icon in a main window ofthe toolbar menu mode screen.

As shown in FIG. 13a , the clock icon 1310 a representing the clockfunction showing the present time is placed on the toolbar 120. If theclock icon 1310 a is dragged from the toolbar 120 and dropped in themain window 130, the control unit 370 detects the movement of the clockicon and checks the clock function matched with the clock icon 1310 afrom a matching table (setting information file). Next, the control unit370 activates the clock function such that an active clock functionobject 1310 b indicating the present time appears in the main window 130as shown in FIG. 13b . In this exemplary embodiment, the active clockfunction object 1310 b may appear in the form of an analog clock imageor a digital clock image.

FIG. 14 is a flowchart illustrating an exemplary function executionprocess of FIGS. 13a and 13 b.

Referring to FIGS. 13a, 13b , and 14, the control unit 370 detects themovement of the clock icon 1310 a from the toolbar 120 to the mainwindow 130 in step S1410. The control unit 370 recognizes the clockfunction matched with the clock function icon and checks the presenttime in step S1420. Finally, the control unit 370 displays the activeclock function object 1310 b indicating the present time in the mainwindow 130 in step S1430.

Third Exemplary Embodiment

FIGS. 15a to 15c are diagrams illustrating operations of a function in atoolbar menu mode of a user interface method according to an exemplaryembodiment of the present invention. In this exemplary embodiment, thefunction execution process is described with reference to activation ofa photo album function by dragging a photo album icon representing thephoto album function from the toolbar and dropping the photo album iconin the main window.

As shown in FIG. 15a , the photo album icon 1510 representing the photoalbum function is placed on the toolbar 120. If the photo album icon1510 is dragged from the toolbar 120 and dropped in the main window 130,the control unit 370 detects the movement of the photo album icon andchecks the photo album function matched with the photo album icon 1510with reference to the matching table. Next, the control unit 370activates the photo album function such that an active photo albumfunction object 1520 appears in the main window 130 as shown in FIG. 15b. In the illustrated example of FIG. 15b , the active photo albumfunction object 1520 is composed with a presentation window 1520 a forpresenting a photo stored with the photo album function and album andsettings buttons 1520 b and 1520 c, respectively for executingsub-functions associated with the photo album function. The album button1520 b can be configured as a button for switching between folderscontaining photos, and the settings button 1520 c can be configured as abutton for selecting a photo provided by the photo album function as abackground image of the mobile terminal.

The active photo album object 1520 is provided with a pair of navigationbuttons such that, when a touch is detected on one of the navigationbuttons, the control unit 370 controls such that the photo presented inthe presentation window is shifted in a direction indicated by thetouched navigation button. Also, when a touch is detected on the albumbutton 1520 b, the control unit controls such that a folder list ispresented for selecting a folder from the folder list.

Also, when a touch is detected on the setting button 1520 c, the controlunit 370 controls such that the current image presented in thepresentation window 1520 a is set to be the background image of themobile terminal as shown in FIG. 15 c.

FIG. 16 is a flowchart illustrating an exemplary function executionprocess.

Referring to FIGS. 15a to 15c and 16, the control unit 370 detects themovement of the photo album function icon 1510 from the toolbar 120 tothe main window 130 in step S1610 and presents an image registered withthe photo album function represented by the photo album function icon1510 in step S1620. The control unit 370 detects a touch on thetouchscreen panel 360 b and determines whether the touch is detected ona navigation button 1530 in step S1630. If the touch is detected on anavigation button 1530, the control unit 370 controls such that theimage is shifted corresponding to the navigation button 1530 in stepS1640. Otherwise, if the touch is not detected on the navigation buttons1530, the control unit 370 determines whether a touch is detected on thealbum button 1520 b of the photo album function object 1520 in stepS1650. If the touch is detected on the album button 1520 b, the controlunit 370 controls such the folder list is presented in order for theuser to select a folder from the folder list in step S1660. If the touchis not detected on the album button 1520 b, the control unit 370determines whether a touch is detected on the setting button 1520 c instep S1670. If the touch is detected on the setting button 1520 c, thecontrol unit controls such that the current image presented in thepresentation window 1520 a is set for the background image of the mobileterminal in step S1680.

Fourth Exemplary Embodiment

FIGS. 17a to 17c are diagrams illustrating operations of a function in atoolbar menu mode of a user interface method according to an exemplaryembodiment of the present invention. In this example, the functionexecution process is described with reference to activation of a Top-3function by dragging a Top-3 function icon representing the Top-3function from the toolbar and dropping the Top-3 function icon in themain window.

The Top-3 function refers to a function for presenting information aboutregistered members selected from a phonebook on the toolbar menu modescreen simultaneously such that the user can make a voice call, a videocall, or a message call to the registered member immediately. In orderto use the Top-3 function, the user must register the members for theTop-3 function. Also, it should be understood that the number of usersis not limited to three but may include more or fewer users at theselection of the user.

As shown in FIG. 17a , the Top-3 function icon 1710 representing theTop-3 function is placed on the toolbar 120. If the Top-3 function icon1710 is dragged from the toolbar 120 and dropped in the main window 130,the control unit 370 detects the movement of the Top-3 function icon1710 and checks the Top-3 function match with the Top-3 function icon1710 with reference to the matching table. Next, the control unit 370activates the Top-3 function such that an active Top-3 function object1720 appears in the main window 130 as shown in FIG. 17b . The activeTop-3 function object 1720 is composed of three presentation windows1720 a, 1720 b, and 1720 c for presenting images associated with theregistered members. The three presentation windows 1720 a, 1720 b, and1720 c can be aligned in the vertical or horizontal direction. In FIG.17b for example, the three presentation windows 1720 a, 1720 b, and 1720c are aligned in vertical direction. The control unit 370 controls suchthat the three presentation windows 1720 a, 1720 b, and 1720 c presentimages set in association with the individual registered members. When atouch is detected on one of the three presentation windows 1720 a, 1720b, and 1720 c, the control unit 370 controls such that the touchedpresentation window is enlarged by a certain percentage. At this time,the enlarged presentation window is presented with submenu buttons 1730a, 1730 b, and 1730 c, and the other two presentation windows arearranged at one side of the enlarged presentation window as illustratedin FIG. 17 c.

If the touch is detected on a first presentation window 1720 a, then thecontrol unit 370 controls such that the first presentation window 1720 ais enlarged by the certain percentage together with the submenu buttons1730 a, 1730 b, and 1730 c at the bottom side of the enlargedpresentation window 1720 a, as shown in FIG. 17c . In this exemplaryembodiment, the submenu buttons are designated for a voice call button1730 a, a message button 1730 b, and a video call button 1730 c. When atouch is detected on the voice call button 1730 a, the control unit 370controls such that a voice call is made to the phone number registeredwith the image presented on the enlarged presentation window. Of course,the submenu buttons may be designated with other functions as supportedby the mobile terminal or as otherwise appropriate for the function.

As shown in FIG. 17c , the control unit 370 also controls such that thetwo other presentation windows 1720 b and 1720 c are arranged at oneside of the enlarged presentation window 1720 a.

FIG. 18 is a flowchart illustrating an exemplary function executionprocess of FIGS. 17a to 17 c.

Referring to FIGS. 17a to 17c and 18, the control unit 370 detects themovement of the Top-3 function icon 1710 from the toolbar 120 to themain window 130 in step S1810 and displays an active Top-3 functionobject 1720 having presentation windows 1720 a, 1720 b, and 1720 cpresenting individual images associated with the members registered forthe Top-3 function in step S1820. The control unit 370 determineswhether a touch is detected on any of the presentation windows 1720 a,1720 b, and 1720 c in step S1830. If a touch is detected on apresentation window, the control unit 370 controls such that the touchedpresentation window is enlarged by a certain percentage together withsubmenu buttons 1730 a, 1730 b, and 1730 c in step S1840. Next, thecontrol unit 370 controls such that the untouched presentation windowsare arranged at one side of the enlarged presentation window in stepS1850. Next, the control unit 370 determines whether a touch is detectedon any of the submenu buttons 1730 a, 1730 b, and 1730 c in step S1860.If a touch is detected on a submenu button, the control unit 370controls such that a function linked to the touched submenu button isexecuted in step S1870.

Fifth Exemplary Embodiment

FIGS. 19a and 19b are diagrams illustrating operations of a function ina toolbar menu mode of a user interface method according to an exemplaryembodiment of the present invention, and FIG. 19c is a screenshotillustrating a toolbar menu mode screen displayed in association of thefunction execution process of FIGS. 19a and 19b . In this example, thefunction execution process is described with reference to activation ofa Bluetooth function. Since a Bluetooth link establishment procedurebetween the mobile terminal and a Bluetooth device is considered obviousto those skilled in the art, detailed description on the Bluetooth linkestablishment procedure is omitted for sake of convenience.

When the mobile terminal operates in a Bluetooth communication mode, thecontrol unit 370 controls to scan the Bluetooth radio frequency todiscover Bluetooth devices in its Bluetooth radio range. In the presentexample, the mobile terminal discovers four Bluetooth devices A, B, Cand D within the Bluetooth radio range. Accordingly, the control unitcontrols to arrange the device icons 1920, 1930, 1940, and 1950representing Bluetooth devices A, B, C and D discovered in the Bluetoothradio range around a Bluetooth function icon 1910, as shown in FIG. 19a.

If one (in this example, device icon 1940) of the device icons 1920,1930, 1940, and 1950 is dragged and dropped on the Bluetooth functionicon 1910 positioned at the center of a Bluetooth communication modescreen as shown in FIG. 19b , the control unit 370 detects the movementof the device icon 1940 and controls the Bluetooth unit 320 (see FIG. 3)such that the Bluetooth unit 320 establishes a Bluetooth link with theBluetooth device C represented by the device icon 1940.

As shown in FIG. 19c , the Bluetooth devices discovered by the mobileterminal are arranged around the Bluetooth icon in the forms of deviceicons together with individual device names in a Bluetooth mode screen.

FIG. 20 is a flowchart illustrating an exemplary function executionprocess.

Referring to FIGS. 19a to 19c and 20, the control unit 370 detects thatthe mobile terminal enters the Bluetooth communication mode in stepS2010 and scans the Bluetooth radio frequency to discover neighborBluetooth devices in step S2020. Sequentially, the control unit 370arranges device icons 1920, 1930, 1940, and 1950 representing thediscovered Bluetooth devices A, B, C, and D in step S2030. The controlunit 370 determines whether any of the device icons 1920, 1930, 1940,and 1950 are dragged and dropped on the Bluetooth function icon 1910arranged at the center of the Bluetooth communication mode screen instep S2040. If a device icon is dragged and dropped on the Bluetoothfunction icon 1910, the control unit 370 controls such that Bluetoothunit 320 (see FIG. 3) establishes a Bluetooth link between the mobileterminal and the Bluetooth device represented by the device icon in stepS2050.

As described above, the user interface method and apparatus according toexemplary embodiments of the present invention enables activating afunction by dragging an icon representing the function from a toolbarand dropping the icon on a main window provided in a toolbar menu modescreen displayed on a touchscreen of a mobile terminal, whereby a usercan execute functions provided by the terminal in intuitive manner.

Also, the user interface method and apparatus of the present inventionallows the user to arrange graphical objects such as toolbar andfunction icons placed on the toolbar and active function objectspresenting information provided by the functions represented by thefunction icons on the touchscreen, thereby improving decorative effectas well as interactivity of the touchscreen as user interface.

While the invention has been shown and described with reference tocertain exemplary embodiments thereof, it will be understood by thoseskilled in the art that various changes in form and details may be madetherein without departing from the spirit and scope of the invention asdefined by the appended claims and their equivalents.

What is claimed is:
 1. A mobile terminal comprising: a sensor configuredto detect a rotation of the mobile terminal; a touch screen configuredto display a screen and detect a touch input; and at least one processorconfigured to control the touch screen to: display a screen comprising asecond region for presenting a toolbar comprising at least one userinterface (UI) element corresponding to a function of at least onefunction installed in the mobile terminal, and a first region fordisplaying activation of the function represented by the UI element,maintain, in response to a change of an orientation of the mobileterminal between a portrait orientation and a landscape orientationaccording to the rotation of the mobile terminal, the second region forthe toolbar at a position that is relatively the same as a position ofthe second region for the toolbar before the change of the orientationof the mobile terminal, and change, in response to the change of theorientation of the mobile terminal, the orientation of the UI elementwithin the second region according to the changed orientation of themobile terminal.
 2. The apparatus of claim 1, wherein the at least oneprocessor is further configured to change the orientation of the firstregion in accordance with the changed orientation of the mobileterminal.
 3. The apparatus of claim 1, wherein the at least oneprocessor is further configured to activate the function represented bythe UI element when the UI element is dragged from the toolbar anddropped in the first region using the touch input on the touch screenunit.
 4. The apparatus of claim 1, wherein the at least one processor isfurther configured to maintain the second region for the toolbar at oneof a center position, a left position, or a right position of thescreen, that is substantially the same as a position of the secondregion for the toolbar before the change of the orientation of themobile terminal.
 5. The apparatus of claim 1, wherein the UI elementcomprises an icon symbolizing the function represented by the UIelement.
 6. The apparatus of claim 5, wherein the at least one processoris further configured to: retrieve and present a function list listingfunctions that can be registered with the toolbar, create a matchingtable that matches functions selected from the function list withcorresponding icons, and activate, when the drag and drop activity ofthe icon is detected, the function matched with the icon in the matchingtable.
 7. The apparatus of claim 1, wherein the screen comprises amarker such that, when a touch is detected on the marker and the toolbaris not shown, the toolbar is displayed, and wherein, when a touch isdetected on the marker and the toolbar is shown, the toolbar is hidden.8. The apparatus of claim 6, wherein the screen comprises a third regionwhich presents information on the function when a touch is detected onthe icon representing the function.
 9. The apparatus of claim 6, whereinthe toolbar comprises a photo album function icon representing a photoalbum function, and wherein the at least one processor is furtherconfigured to, when a drag and drop activity of the photo album functionicon is detected on the touch screen unit, control the displaying of anactive photo album function object comprising a presentation window forpresenting an image stored in association with the photo album functionand a first submenu button and a second submenu button for executingfunctions provided by the photo album function.
 10. The apparatus ofclaim 1, wherein the at least one processor is further configured toremove the UI element dragged and dropped in the first region from thetoolbar.
 11. The mobile terminal of claim 1, wherein the at least oneprocessor is further configured to, in response to the change of theorientation of the mobile terminal according to the rotation of themobile terminal, control the touch screen to: maintain a position of thetoolbar that is relatively the same as a position of the toolbar beforethe change of the orientation of the mobile terminal, and change theorientation of the UI element in a direction opposite to the rotation ofthe mobile terminal.
 12. The mobile terminal of claim 1, wherein the atleast one processor is further configured to, in response to the changeof the orientation of the mobile terminal, control the touch screen to:maintain a position of the toolbar that is relatively the same as aposition of the toolbar before the change of the orientation of themobile terminal, and maintain a position of submenu buttons that isrelatively the same as a position of the submenu buttons before thechange of the orientation of the mobile terminal.
 13. The mobileterminal of claim 1, wherein the at least one processor is furtherconfigured to, in response to the change of the orientation of themobile terminal, control the touch screen to: maintain a position of thetoolbar that is relatively the same as a position of the toolbar beforethe change of the orientation of the mobile terminal, maintain aposition of submenu buttons that is relatively the same as a position ofthe submenu buttons before the change of the orientation of the mobileterminal, and change the orientation of the UI element in the toolbarand icons in the submenu buttons according to the changed orientation ofthe mobile terminal.
 14. The mobile terminal of claim 1, wherein the atleast one processor is further configured to, in response to the changeof the orientation of the mobile terminal according to the rotation ofthe mobile terminal, control the touch screen to: maintain a position ofthe toolbar that is relatively the same as a position of the toolbarbefore the change of the orientation of the mobile terminal, maintain aposition of submenu buttons that is relatively the same as a position ofthe submenu buttons before the change of the orientation of the mobileterminal, and change the orientation of the UI element in the toolbarand icons in the submenu buttons in a direction opposite to the rotationof the mobile terminal.
 15. An interface method for a mobile terminalcomprising a touch screen unit, the method comprising: displaying in ascreen a second region for presenting a toolbar comprising at least oneuser interface (UI) element corresponding to at least one functioninstalled in the mobile terminal; displaying in the screen a firstregion for displaying activation of the function represented by the UIelement; detecting a rotation of the mobile terminal; maintaining, inresponse to a change of an orientation of the mobile terminal between aportrait orientation and a landscape orientation according to therotation of the mobile terminal, the second region for the toolbar at aposition that is relatively the same as a position of the second regionfor the toolbar before the change of the orientation of the mobileterminal; and changing an orientation of the UI element within thesecond region according to the changed orientation of the mobileterminal.
 16. The interface method of claim 15, further comprisingchanging an orientation of the first region in accordance with thechanged orientation of the mobile terminal.
 17. The interface method ofclaim 15, further comprising activating the function associated with theUI element when the UI element is dragged from the toolbar and droppedin the first region using the touch input on the touch screen unit. 18.The interface method of claim 15, wherein the maintaining compriseslocating the second region for the toolbar at one of a center position,a left position and a right position of the screen, that issubstantially the same as a position of the second region for thetoolbar before the change of the orientation of the mobile terminal. 19.The interface method of claim 15, wherein the UI element comprises anicon symbolizing the function represented by the UI element.
 20. Theinterface method of claim 19, further comprising: displaying, when themobile terminal enters a toolbar menu mode, a function list listing atleast one function that can be registered with the toolbar; and creatinga matching table which matches functions selected from the function listwith corresponding icons.
 21. The interface method of claim 20, furthercomprising: determining, when a touch is detected on a correspondingicon, information on the function represented by the icon from a settinginformation file; and presenting the information of the function in athird region.
 22. The interface method of claim 20, further comprisingrendering, when at least two active function objects are overlapped inthe first region, the active function objects to appear in asemi-transparent state.
 23. The interface method of claim 20, furthercomprising arranging, when a touch is detected on one of the overlappedactive function objects, the touched active function object moved infront of the other active function objects on the screen.
 24. Theinterface method of claim 17, further comprising: removing the UIelement dragged and dropped in the first region from the toolbar. 25.The interface method of claim 15, further comprising: in response to thechange of the orientation of the mobile terminal according to therotation of the mobile terminal, maintaining a position of the toolbarthat is relatively the same as a position of the toolbar before thechange of the orientation of the mobile terminal; and changing theorientation of the UI element in a direction opposite to the rotation ofthe mobile terminal.
 26. The interface method of claim 15, furthercomprising: in response to the change of the orientation of the mobileterminal, maintaining a position of the toolbar that is relatively thesame as a position of the toolbar before the change of the orientationof the mobile terminal; maintaining a position of submenu buttons thatis relatively the same as a position of submenu buttons before thechange of the orientation of the mobile terminal; and changing theorientation of the UI element according to the changed orientation ofthe mobile terminal.
 27. The interface method of claim 15, furthercomprising: in response to the change of the orientation of the mobileterminal, maintaining a position of the toolbar that is relatively thesame as a position of the toolbar before the change of the orientationof the mobile terminal; maintaining a position of submenu buttons thatis relatively the same as a position of the submenu buttons before thechange of the orientation of the mobile terminal; and changing theorientation of the UI element in the toolbar and icons in the submenubuttons according to the changed orientation of the mobile terminal. 28.The interface method of claim 15, further comprising: in response to thechange of the orientation of the mobile terminal, maintaining a positionof the toolbar that is relatively the same as a position of the toolbarbefore the change of the orientation of the mobile terminal; maintaininga position of submenu buttons that is relatively the same as a positionof the submenu buttons before the change of the orientation of themobile terminal; and changing the orientation of the UI element in thetoolbar and icons in the submenu buttons in a direction opposite to therotation of the mobile terminal.